Skip to content
This repository was archived by the owner on Dec 27, 2023. It is now read-only.

support postcss 8 plugins, closes #5 #6

Merged
merged 10 commits into from
Sep 18, 2020

Conversation

goto-bus-stop
Copy link
Contributor

This PR adds support for postcss 8 while maintaining support for postcss 7. In postcss 8 plugins no longer provide their own .process() method, so this package has to depend on postcss itself to test plugins.

@Semigradsky
Copy link
Member

@jonathantneal Hi! How about merge and publish new release?
Or add somebody to csstools if you haven't enough time.

@jonathantneal
Copy link
Collaborator

@Semigradsky, yes, I’ll merge now and do an immediate release. I also want to talk about getting other maintainers on board. Like yourself, immediately. I have started up a monorepo a couple times. I need partners on this project. It can be done fast. Would you have time today or this weekend to team up?

@jonathantneal jonathantneal merged commit 17a2bbd into csstools:master Sep 18, 2020
@goto-bus-stop goto-bus-stop deleted the postcss8 branch September 18, 2020 14:25
@Semigradsky
Copy link
Member

@jonathantneal I can't now, but I will be available after this weekend.

romainmenke pushed a commit to csstools/postcss-plugins that referenced this pull request Jan 16, 2022
romainmenke added a commit to csstools/postcss-plugins that referenced this pull request Jan 20, 2022
* 1.0.0

* 1.1.0

* 1.2.0

* 1.2.1

* 1.2.2

* 1.3.0

* 1.3.1

- Update project settings

* 2.0.0

- Updated: Support for PostCSS v6
- Updated: Support Node v4
- Added: Another test

* 2.0.1

* Better support failing tests

* Support specifying alternative plugin(s)

* Update devDependencies

* 2.1.0

* New option: processOptions

* Document features

* Update devDependencies

* 2.2.0

* 3.0.0

* 3.0.0

* Log caught errors and update README with correct options

* 4.0.0

* 5.0.0

* Update project configuration

* Fix CLI typo in README.md

The CLI (i.e. "arguments") instructions included an `=` sign; the equals sign is not accurate nor necessary. Just to be sure, I tested:

1. I copied `.tape.js` as `.tape.test.js`, and removed several test cases.
2. Command `postcss-tape --config=./tape.test.js # used existing `/.tape.js` (saw many test cases).
3. Command `postcss-tape --config=./tape.test.js # used new file `/.tape.test.js` (saw few test cases).

* Fix bug with tests for errors

* Cleanup how options are taken in

* Fix how an error is handled

* Update dependencies

* 5.0.1

* Fix an issue with loading a test plugin

* 5.0.2

* Update dependencies

* support postcss 8 plugins, closes csstools/postcss-tape#5 (csstools/postcss-tape#6)

* Support Node 10 (csstools/postcss-tape#7)

* Update CHANGELOG.md

* 6.0.0

* Update project conventions

* 6.0.1

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* changelog

* merge

* tests

* tests

* simplify

* some docs

* docs, more tests and fixes

* add docs for postcss version updates

* fixes

* more tests

* Apply suggestions from code review

* more tests

* code comment

* try relative path require/import

* typo

* fix

* fix

* fix

* more docs

* document what to do after node 20 released

Co-authored-by: Jonathan Neal <jonathantneal@hotmail.com>
Co-authored-by: Philip Bordallo <git@philipbordallo.com>
Co-authored-by: Wesley B <wesleyboar@users.noreply.github.com>
Co-authored-by: Renée Kooi <renee@kooi.me>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants